ci: re-pin container standard to 35f31f3 to restore Container CI#28
Merged
Conversation
The reusable container workflows were pinned at `58d011d`, whose `_container-ci.yml`
references `${{ runner.temp }}` from a job-level `env:` block. The `runner` context does
not exist there, so GitHub rejects the workflow at validation time: every Container CI run
is created with ZERO jobs and reports a bare "failure".
Container CI is therefore currently dead in this repo — it reports failure without ever
executing a single job. This re-pins both the CI and release callers to the corrected
standard revision `35f31f3`, which moves that variable into valid step-level scope and
restores the PR-time gate.
Released images are unaffected (container-release.yml is a separate file and ran fully),
so this is a CI-infrastructure re-pin only: no version bump, no CHANGELOG entry, no tag,
no re-release.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011RiEgEWKERebTxeD2fvsph
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The reusable container workflows were pinned at
58d011d, whose_container-ci.ymlreferences
${{ runner.temp }}from a job-levelenv:block. Therunnercontext doesnot exist there, so GitHub rejects the workflow at validation time: every Container CI run
is created with ZERO jobs and reports a bare "failure".
Container CI is therefore currently dead in this repo — it reports failure without ever
executing a single job. This re-pins both the CI and release callers to the corrected
standard revision
35f31f3, which moves that variable into valid step-level scope andrestores the PR-time gate.
Released images are unaffected (container-release.yml is a separate file and ran fully),
so this is a CI-infrastructure re-pin only: no version bump, no CHANGELOG entry, no tag,
no re-release.